Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1992

reference: 210-tree-1
name: 1992
tree-preservation-order: undefined
210-tpo-1
uprn
address-text
point: POINT (-0.988011 50.797759)
geometry: MULTIPOLYGON (((-0.987954 50.797753,-0.987957 50.797764,-0.987964 50.797774,-0.987977 50.797782,-0.987993 50.797788,-0.988010 50.797790,-0.988028 50.797788,-0.988044 50.797783,-0.988056 50.797775,-0.988065 50.797765,-0.988068 50.797754,-0.988065 50.797743,-0.988057 50.797733,-0.988045 50.797725,-0.988029 50.797720,-0.988012 50.797718,-0.987994 50.797719,-0.987978 50.797724,-0.987965 50.797732,-0.987957 50.797742,-0.987954 50.797753)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL